Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(webSocket): fix node.js example #2441

Merged
merged 1 commit into from
Apr 3, 2017
Merged

Conversation

jsayol
Copy link
Contributor

@jsayol jsayol commented Mar 4, 2017

Description: Fixes the example showing the usage of WebSocketSubject on Node.js.

Related issue (if exists): none

@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.688% when pulling 6b6fc86 on jsayol:patch-1 into 7c41c08 on ReactiveX:master.

Copy link
Member

@benlesh benlesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use socket$ and Observable.webSocket

@@ -60,12 +60,11 @@ export class WebSocketSubject<T> extends AnonymousSubject<T> {
*
* import { w3cwebsocket } from 'websocket';
*
* let socket = new WebSocketSubject({
* let subject = new WebSocketSubject({
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, I think we should go with socket$ everywhere, and use Observable.webSocket rather than new WebSocketSubject.

I'm glad you caught this, though. Would you mind making this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.688% when pulling a49c2d0 on jsayol:patch-1 into 7c41c08 on ReactiveX:master.

@jsayol
Copy link
Contributor Author

jsayol commented Mar 5, 2017

Let me know if I should squash the commits, I couldn't find anything about it in the contributing guidelines :)

Edit: I just noticed that it does say to do so. I'll do in a minute.

@coveralls
Copy link

coveralls commented Mar 5, 2017

Coverage Status

Coverage remained the same at 97.688% when pulling 6b6fc86 on jsayol:patch-1 into 7c41c08 on ReactiveX:master.

@kwonoj kwonoj added the docs Issues and PRs related to documentation label Mar 12, 2017
@benlesh benlesh merged commit 736d48d into ReactiveX:master Apr 3, 2017
@lock
Copy link

lock bot commented Jun 6, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
docs Issues and PRs related to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants